home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: chang.unx.sas.com!walker
- From: walker@chang.unx.sas.com (Doug Walker)
- Subject: Re: Ceck out this bug. Wh
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <DotxtC.K13@unx.sas.com>
- Date: Mon, 25 Mar 1996 15:31:59 GMT
- X-Nntp-Posting-Host: chang.unx.sas.com
- References: <1120.6643T91T406@login.eunet.no> <885.6646T9T693@login.eunet.no> <755.6652T1180T2805@login.eunet.no> <64_5607@tna.nullnet.fi>
- Organization: SAS Institute Inc.
-
- In article <64_5607@tna.nullnet.fi>,
- Marcus Alanen <marcus.alanen@tna.nullnet.fi> wrote:
- >>>You should change the value in your code by adding the following line
- >>>external to any function:
- >>> long _STKNEED = 1024;
- >> Yeah, it will do, but its a litte anoying having it in the source
- >> though.
- >
- > Hmm... isn't there a way to know how much stack space a function
- > allocates? THen it would be possible for the compiler to automatically
- > set the "long _STKNEED = xxxxx" line when compiling the program.
- > Or have I missed something here?-)
-
- Yes, it is possible to know how much stack space a function allocates. This
- is indeed how stack extension works in the first place. But _STKNEED is not
- used to provide stack space for the current function - it is used to provide
- stack space for any functions CALLED by the current function, if those
- called functions are not compiled with stack extension.
-
- --Doug
- --
- *****
- *|_o_o|\\ Doug Walker walker@unx.sas.com
- *|. o.| ||
- | o |// Any opinions are mine, not those of SAS Institute, Inc.
- ======
-